[HF] Fee output logic cleanup, allow 0-value fees #160
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
instagibbs
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previous logic, aside from allowing 0-fee outputs, was completely duplicated in other sections of the code.
The value-checking of outputs is already done in
CheckTransaction,VerifyAmountsandVerifyCoinbaseAmount, so no need to check again in another context.I can not recall why we disallowed 0-value fees initially, but the new logic is cleaner since we now always allow 0-value outputs as long as they're
IsUnspendable, which fees are a smaller subset of.I have also added more tests.